-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UIORGS-398: modify summary display in organization view mode #575
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code LGTM. Please don't forget a CHANGELOG.md entry.
Boolean(organization.isVendor && organization.isDonor) && ( | ||
<Accordion | ||
id={donorContacts} | ||
label={ORGANIZATION_SECTION_LABELS[donorContacts]} | ||
> | ||
{/* | ||
TODO: add donor contacts list component https://issues.folio.org/browse/UIORGS-394 | ||
*/} | ||
</Accordion> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Boolean(foo && bar)
seems superfluous to me sincefoo && bar
will already evaluate toboolean
but 🤷- I am not a fan of placeholder stories that insert a broken/empty UI element. Essentially, they add a bug ("accordion is present but has no content"). I guess that's an issue to take up with your PO, but I would strongly prefer UIORGS-398 to be merged after UIORGS-394 was complete.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure. Thank you for your comments.
7bbe67c
to
36f3c02
Compare
Kudos, SonarCloud Quality Gate passed! |
Purpose
UIORGS-398 - modify summary display in organization view mode
Approach
Screen.Recording.2023-10-17.at.2.02.46.PM.mov
TODOS and Open Questions
Learning
Pre-Merge Checklist
Before merging this PR, please go through the following list and take appropriate actions.
If there are breaking changes, please STOP and consider the following:
Ideally all of the PRs involved in breaking changes would be merged in the same day to avoid breaking the folio-testing environment. Communication is paramount if that is to be achieved, especially as the number of intermodule and inter-team dependencies increase.
While it's helpful for reviewers to help identify potential problems, ensuring that it's safe to merge is ultimately the responsibility of the PR assignee.